View 0801831_9082947.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1description axioline ? f bus coupler for sercos axl f bk s3 ? phoenix contact data sheet valid from firmware version ? 1.10. the bus coupler is intended for use within a third-generation sercos network and represen ts the link to the axioline ? f system. up to 63 axioline ? f devices can be connected to an existing sercos network with the help of the bus coupler. features of sercos ?2 ethernet-ports ? rotary coding switches for setting the sercos address ? transmission speed of 100 ? mbps with a minimum ser- cos cycle time of 31.25 ? s ? sercos diagnostic led ? certified according to sercos v1.12 ? supports sercos v1.31 ? fsp-io (function specific profile-io) for modular i/o devices ? a maximum of 8 connecti ons are supported (max. 4 consumer and max. 4 producer connections) ? cross communication is possible up to reaching the maximum number of connections ?synchronization features of axioline f ? up to 63 additional axioline ? f devices can be connect- ed ? typical cycle time of the axioline ? f local bus is around 10 ? s ? runtime in the bus coupler is negligible (goes to 0 ? s) ?firmware can be updated ? diagnostic and status indicators this data sheet is only valid in association with the um ? en ? axl ? f ? sys ? inst user manual. you can find further information on sercos in the um de sercos sys user manual. make sure you always use the latest documentation. it can be downloaded from the product at phoenixcontact.net/products . you will always find the current sddml-files here. 105610_en_02 2015-11-10
axl f bk s3 105610_en_02 phoenix contact 2 2table of contents 1 description ................................................................................................................... ........... 1 2 table of contents ............................................................................................................. ........ 2 3 ordering data ................................................................................................................. ......... 3 4 technical data ................................................................................................................ ......... 4 5 internal circuit diagram ...................................................................................................... ...... 6 6 connection of sercos and supply ............................................................................................ 7 7 connection example............................................................................................................ .... 7 8 configuration via rotary encoding switch ................................................................................. 8 9 local status and diagnostic indicators ..................................................................................... 9 10 sercos ....................................................................................................................... ............ 12 11 sercos parameter ............................................................................................................. ..... 16 12 access to pdi objects........................................................................................................ .... 20 13 mapping method............................................................................................................... ..... 20 14 tunnel method................................................................................................................ ....... 21 15 reset button ................................................................................................................. ......... 25 16 service interface............................................................................................................ ........ 26 17 startup...................................................................................................................... ............. 26 18 firmware update.............................................................................................................. ...... 28
axl f bk s3 105610_en_02 phoenix contact 3 description type order no. pcs./pkt. axioline ? f bus coupler for sercos (includi ng bus base module and connec- tor) axl f bk s3 2701686 1 3ordering data accessories type order no. pcs./pkt. axioline ? f bus base module for housing type bk (replacement item) axl bs bk 2701422 5 axioline ? f short power connector (for e.g., axl ? f ? bk ...) (replacement item) axl cn s/ul 2701421 5 rj45 connector, shielded, with bend pr otection sleeve, 2 pieces, gray for straight cables, for assembly on site. for connections that are not crossed, it is recommended that you use the conne ctor set with gray bend protection sleeve. (connector/adapter) fl plug rj45 gr/2 2744856 1 rj45 connector, shielded, with bend protection sleeve, 2 pieces, green for crossed cables, for assembly on site. for connections that are crossed, it is recommended that the connector set with green bend protection sleeves is used. (connector/adapter) fl plug rj45 gn/2 2744571 1 cat5-sf/utp cable (j-02ys(st)c hp 2 x 2 x 24 awg), heavy-duty instal- lation cable, 2 x 2 x 0.22 mm2, solid co nductor, shielded, outer sheath: 7.8 mm diameter, inner sheath: 5.75 mm 0.15 mm diameter (cable/conduc- tor) fl cat5 heavy 2744814 1 cat5-sf/utp cable (j-li02ys(st)c h 2 x 2 x 26 awg), light-duty, flexi- ble installation cable 2 x 2 x 0.14 mm2 , stranded, shielded, outer sheath: 5.75 mm 0.15 mm diameter (cable/conductor) fl cat5 flex 2744830 1 crimping pliers, for assembling the rj45 plugs fl plug rj45..., for as- sembly on site (tools) fl crimptool 2744869 1 zack marker strip for axioline ? f (device labeling), in 2 x 20.3 mm pitch, un- printed, 25-section, for in dividual labeling with b-stift 0.8, x-pen, or cms-p1-plotter (marking) zb 20,3 axl unprinted 0829579 25 zack marker strip, flat, in 10 mm pitch, unprinted, 10-section, for individual labeling with m-pen 0,8, x-pen, or cms-p1-plotter (marking) zbf 10/5,8 axl unprinted 0829580 50 insert label, roll, white, unlabele d, can be labeled with: thermomark roll, thermomark roll x1, thermomark x, thermomark s1.1, mounting type: snapped into marker carrier, lettering field: 35 x 18.7 mm (marking) emt (35x18,7)r 0801831 1 connecting cable, for connecting the controller to a pc for pc worx and logic+, usb a to micro usb b, 2 m in length. (cable/conductor) cab-usb a/micro usb b/2,0m 2701626 1 documentation type order no. pcs./pkt. user manual, english, axioline ? f: system and installation um en axl f sys inst - - user manual, english, axioline f: dia gnostic registers, and error messages um en axl f sys diag - - user manual, english, sercos system ma nual for i/o devices um en sercos sys - - application note, english, updating the firmware of an axioline ? f bus coupler ah en tftp firmware update axl f bk - -
axl f bk s3 105610_en_02 phoenix contact 4 dimensions (nominal sizes in mm) width 45 mm height 125.9 mm depth 74 mm note on dimensions the depth is valid when a th ? 35-7.5 din rail is used (according to en ? 60715). 4 technical data 45 74 125,9 122,4 general data color traffic grey a ral 7042 weight 177 g (with connector and bus base module) ambient temperature (operation) -25 c ... 60 c (mount ing position: wall mounting on horizontal din rail) -25 c ... 55 c (mounting position: any) ambient temperature (storage/transport) -40 c ... 85 c permissible humidity (operation ) 5 % ... 95 % (non-condensing) permissible humidity (storage/transport) 5 % ... 95 % (non-condensing) air pressure (operation) 70 kpa ... 106 kpa (up to 3000 m above sea level) air pressure (storage/transport) 70 kpa ... 106 kpa (up to 3000 m above sea level) degree of protection ip20 protection class iii, iec 61140, en 61140, vde 0140-1 mounting position any (observe temperature derating) connection data designation axioline ? f connector connection method push-in connection conductor cross section solid / stranded 0.2 mm2 ... 1.5 mm2 / 0.2 mm2 ... 1.5 mm2 conductor cross section [awg] 24 ... 16 stripping length 8 mm please observe the information provided on conductor cross sections in the ?axioline ? f: system and installation? user manual.
axl f bk s3 105610_en_02 phoenix contact 5 interface sercos number 2 connection method rj45 socket, auto negotiation and auto crossing transmission speed 100 mbit/s (full duplex) cycle time 31.25 s transmission physics ethernet in rj45 twisted pair transmission length max. 100 m interface axioline ? f ? local bus connection method bus base module transmission speed 100 mbit/s interface service number 1 connection method micro usb type b system limits number of supported devices max. 63 (per station) note: electronics may be damaged when overloaded observe the logic current consumption of each device when configuring an axioline ? f station. it is specified in every module-specific data sheet. the current consumption can differ depending on the individu al module. the permissible number of devices that can be con nected therefore depends on the specific station structure. sercos equipment type sercos slave device profile fsp_io update rate 31.25 s sercos protocols sercos specification sercos specification 1.31 supply of the bus coupler supply of communications power u l 24 v dc maximum permissible voltage range 19.2 v dc ... 30 v dc (including all tolerances, including ripple) current supply at u bus 2 a current consumption from u l typ. 105 ma (without i/os and u l = 24 v) max. 570 ma (with 2 ? a at u bus for the i/os and u l = 24 v) power consumption at u l typ. 2.5 w (without i/os) max. 13.7 w (with 2 ? a load at u bus for the i/os) note: electronics may be damaged when overloaded provide external fuses for the 24 v u l area. the power supply unit must be able to supply four times the nominal current of the external fuse to ensure that it blows in the event of an error. error messages to the higher le vel control or computer system none mechanical tests vibration resistance in acc. with en ? 60068-2-6/iec ? 60068-2-6 5g shock in acc. with en ? 60068-2-27/iec ? 60068-2-27 30g continuous shock according to en ? 60068-2-27/iec ? 60068-2-27 10g
axl f bk s3 105610_en_02 phoenix contact 6 5 internal circuit diagram figure 1 internal wiring of the terminal points key: conformance with emc directive 2004/108/ec noise immunity test in accordance with en 61000-6-2 electrostatic discharge (esd) en ? 61000-4-2/iec ? 61000-4-2 criterion b; 6 kv contact discharge, 8 kv air discharge electromagnetic fields en ? 61000-4-3/iec ? 61000-4-3 criterion a; field intensity: 10 v/m fast transients (burst) en ? 61000-4-4/iec ? 61000-4-4 criterion b, 2 ? kv transient surge voltage (surge) en ? 61000-4-5/iec ? 61000-4-5 criterion b; dc supply lines: 0.5 kv/0.5 kv (symmetrical/asymmetrical); field- bus cable shield: 1 kv conducted interference en ? 61000-4-6/iec ? 61000-4-6 criterion a; test voltage 10 v noise emission test according to en 61000-6-3 radio interference properties en 55022 class b approvals for the latest approvals, please visit phoenixcontact.net/products. 24 v 3.3 v u bus ul u 24 v l service reset fe c d e rdy s sd u bus local bus fe sercos 5v 3.3v rj45 rj45 fe functional earth ground service service interface reset reset button local bus axioline ? f local bus (hereinafter referred to as local bus) rj45 interface power supply unit with electrical isolation microcontroller power supply unit led electrically isolated areas rj45 c xxx xxx
axl f bk s3 105610_en_02 phoenix contact 7 6 connection of sercos and supply 6.1 connecting sercos connecting sercos to the bus coupler via an 8-pos. rj45 connector. the sercos connections are set to autocrossing (auto cross- over). 6.2 connecting the supply voltage - terminal point assignment figure 2 terminal point assignment 7 connection example figure 3 connection of the cables install sercos in accord ance with the specifi- cations in the current "planning and installa- tion guide" (see www.sercos.com). also observe the information in the "sercos system manual for i/o devices" user manual. shielding the shielding ground of the connected twist- ed pair cables is electrically connected with the socket. when connecting network seg- ments, avoid ground loops, potential trans- fers, and voltage equalization currents via the braided shield. observe bending radii the housing dimensions specified under "di- mensions" refer to the bus coupler with i/o connectors without ethernet connection. when installing the bus coupler in a control box, observe the bendin g radii of the cables and the connectors used. if required, use angled rj45 connectors to maintain these bending radii. terminal point color assignment supply voltage input a1, a2 red 24 v dc (u l ) supply of the logic volt- age (internally jumpered) b1, b2 blue gnd reference potential of the supply voltage (internally jumpered) a1 a2 b1 b2 a1 a2 b1 b2 ul 24 v dc (u ) l + - s sd rdy d e sercos 0 2 14 4 6 8 10 12 0 2 4 6 a b c d e f 8 9 s1 x10 s2 x1
axl f bk s3 105610_en_02 phoenix contact 8 8 configuration via rotary encoding switch you can configure the address assignment and other func- tions using rotary encoding switches. after modifying the switch position, restart the bus coupler, as the modification to the switch position does not take ef- fect during operation. figure 4 rotary encoding switch the code results from the sum of s1 ? x ? 10 plus s2 ? x ? 1. the image shows code 77 (7 ? x ? 10 ? + ? 7). 8.1 remote address assignment switch position 00 the standard sercos remote access is activated with this switch position, so that the bus coupler accepts an address assignment e.g., ? via the engineering system. 8.2 manual address assignment switch position 01 ... 159 the devices are automatically assigned addresses as stan- dard. set the sercos address manually with this switch position. remote address assignment, e.g., ? via an engineering tool, is deactivated. 8.3 resetting to the default settings switch position 12c all settings are reset to the delivery state. 8.4 reserved/invalid switch position the device starts with th e previous settings, e.g., ? with the settings that were valid before the device was restarted. s1 s2 code function 0 0 00 remote address assignment 0 ... 15 0 ... 9 01 ... 159 manual address assignment 12 c 12c resetting to the default set- tings other reserved 0 2 4 6 8 a c e 9 b f d x1 s2 0 2 4 6 8 10 12 14 x10 s1 the device is ready for operation after power- ing up, as soon as the rdy led lights up green. a connection to the device however cannot be established in this switch position. as soon as the rdy led lights up green, a new switch position can be selected on the ro- tary encoding switch and the device can be restarted. alternatively, the default setting can also be restored via the reset button (see ?reset but- ton?).
axl f bk s3 105610_en_02 phoenix contact 9 9 local status and diagnostic indicators figure 5 local status and diagnostic indicators lnk act lnk act s sd rdy d e ul designation color meaning state description ul green u l ogic on communications power supply present. off communications power supply not present. sred/or- ange/ green s ercos off nrt mode; no sercos communication orange on cp0 flashing orange/ green cp1: 250 ? ms ? green, 2750 ? ms ? orange flashing orange/ green cp2: 250 ? ms ? green, 250 ? ms ? orange, 250 ? ms ? green, 2250 ? ms ? orange flashing orange/ green cp3: 250 ? ms ? green, 250 ? ms ? orange, 250 ? ms ? green, 250 ? ms ? orange, 250 ? ms ? green, 1750 ? ms ? orange green on cp4 green flashing loop back activated flashing red/orange user error; see chapter on "dia gnostics: bus and user errors" flashing red/green mst loss red on communication error flashing orange (2 ? hz) identification (bit ? 15 in device control); is used for address assign- ment and configuration errors. flashing red (2 ? hz) watchdog error
axl f bk s3 105610_en_02 phoenix contact 10 sd red/or- ange/ green s ub d evice green on sub device is on the operation level (ol) orange on sub device is on the parameterization level (pl) red on error in the sub device (c1d) off sub device is not active. rdy green/ yellow/ red r ea dy green on device is ready for operation. flashing green/yel- low communications power undervoltage or surge voltage overtemperature yellow on firmware/bus coupler is booting yellow flashing firmware update is being performed. flashing yellow/red firmware update has failed. flashing red faulty firmware red on rotary encoding switches are se t to an invalid/reserved position. off device is not ready for operation. d red/yel- low/ green diagnostics of local bus communication run green on the station is ready for oper ation, communication within the station is ok. all data is valid. there are no faults. active green flashing the station is ready for operation, communication within the station is ok. the data is not valid. valid data from the controller/higher-level net- work not available. there is no fault in the module. ready yellow on the station is ready for oper ation, no data exchange taking place. yellow flashing access from startup+ in i/o check mode flashing yellow/red local bus error during active i/o check flashing red local bus error on startup possible causes: configuration cannot be generated, information is missing from a device chip version of a device is axl f bk s3 105610_en_02 phoenix contact 11 e yellow/ red error yellow on i/o warnin g at a local bus device red on i/o error at a local bus device off no i/o messages present. lnk 1/2 green l i nk port 1/2 on connection via ethernet to a module via port 1/2 established off no connection established via port 1/2 act 1/2 yellow act ivity port 1/ 2 flashing transmission or reception of ethernet telegrams at port 1/2 off no transmission or reception of ethernet telegrams at port 1/2 designation color meaning state description
axl f bk s3 105610_en_02 phoenix contact 12 10 sercos 10.1 realtime connections the module supports a maximum of eight realtime data con- nections (s-0-1050.0.x to s- 1050.7.x), with a maximum of four consumer and four producer connections. 10.2 sercos profile, classes and function groups the following sercos profile, classes and function groups are implemented in the module: sercos device model (gdp: generic device profile) sercos communication model (scp: sercos communication profiles) sercos function model (fsp: function specific profile i/o) - basis device model (gdp_basic) - diagnostics (fg_diagnosis) - administration (fg_administration) - device identification (fg_identification) - identification (gdp_id) - function/hardware/firmware/firmware loader version (gdp_rev) - password (gdp_pwd) - state machine (gdp_stm) - state machine (f g_statemachine) - diagnosis trace (gdp_diagt) - diagnosis trace advanced (gdp_diagtadv) - energy status (gdp_ens) - energy (fg_energy) - energy control basic (gdp_encbasic) - energy (fg_energy) - variable configuration (scp_varcfg, scp_varcfg_0x02, scp_varcfg_0x03) - identification of scp classes (fg scp identification) - control of communication phases (fg ? control) - telegram structure (fg telegram setup) - parameters for producer-consumer connection (fg connection) - bus diagnostics (fg bus-diagnostics) - parameters for the non-realtime channel (fg nrt) - timing behavior of the communication (fg timing) - synchronous and isochronous producer and consumer data (scp_sync, scp_sync_0x02) - diagnostics (scp_diag) - control of communication phases (fg ? control) - bus diagnostics (fg bus-diagnostics) - non-realtime channel (scp_nrtpc) - parameters for the non-realtime channel (fg nrt) - consumer connection monitoring; watchdog (scp_wdcon) - parameters for the producer-consumer connection (fg connection) - support for scp_sip and scp_tftp - cyclic communication (scp_cyc) - i/o function profile (fsp_io)
axl f bk s3 105610_en_02 phoenix contact 13 10.3 electronic rating plate the electronic rating plat e comprises the idns s-0- 1300.x.y. see the table in th e ?sercos parameter? section. 10.4 mapping of i/o modules in sercos the local bus devices are assigned to the i/o function groups and structure instances according to the sercos i/o profile. a structure instance (slot) can consist of an i/o function group or several i/o function groups (for example devices with inputs and outputs). the first local bus device occupies slot ? 1 (structure in- stance ? 1), the second occupies slot ? 2 (structure instance ? 2), etc. when assigning the inputs and outputs to the container input data (s-0-1500.0.9) or to the container output data (s- 0-1500.0.5), the input and outp ut process data is always mapped in byte limits in the co ntainer according to the ser- cos i/o profile. the number of bytes of the containers is always even. the following function groups are defined: the bus coupler supports the following idns as configurable data: 10.5 synchronization mechanisms of the bus cou- pler the bus coupler offers three synchronization mechanisms. these are standardized accord ing to the sercos specifica- tion and are configured by the sercos master. the modules, which support a synchronization method, are stored in idn s-0-1050.x.13. asynchronous mode the local bus, which is at a lower level to the bus coupler, runs asynchronously to th e higher-level sercos bus. clock-synchronous mode the local bus, which is at a lower level to the bus coupler, runs synchronously to the higher-level sercos bus. the input and output data is read in or output at a time deter- mined by the master. in doing so, the runtimes of the axioline f modules are taken into consideration. cyclic mode the local bus, which is at a lower level to the bus coupler, runs synchronously to the higher-level sercos bus. the output data is output as quickly as possible and the input data is read in as late as possible. in doing so, the runtimes of the axioline f modules are taken into consideration. function group (fg_io) name s-0-1501 i/o function group unknown s-0-1502 i/o function group digital output s-0-1503 i/o function group digital input s-0-1504 i/o function group analog output s-0-1505 i/o function group analog input s-0-1506 i/o function group counter s-0-1507 i/o function group complex protocol s-0-1508 i/o function group sub bus master s-0-1509 i/o function group sub bus slave s-0-1512 i/o function group plc module s-0-1513 i/o function group motor starter s-0-1514 i/o function group pwm (pulse width modulation) s-0-1515 i/o function group positioning s-0-1516 i/o function group passive in a producer connection in a consumer connection s-0-1500.0.2 s-0-1500.0.1 s-0-1500.0.9 s-0-1500.0.5 fg_io.x.9 fg_io.x.5 fg_io.x.13 fg_io.x.11 s-0-0390 ? this information is stored in the idn. s-0-0187 s-0-0188
axl f bk s3 105610_en_02 phoenix contact 14 10.6 diagnostics: bus and user errors sercos diagnostic code (idn s-0- 0390.0.0) [hex] message meaning corrective local bus error c10f.b001 local bus device is missing device not present install the device or check the contacts and replace a defective device, if necessary. c10f.b002 incorrect local bus device present wrong de- vice an incorrect device was detect ed at the specified location. check the contacts, replace a defective device, if necessary or adapt the configuration. c10e.b012 local bus device pe- ripheral or applica- tion error error in a local bus de- vice see corresponding data sheet. device error read out via idn 1500.0. 32 to ascertain which device and possibly which channel is affected and check the contact, parameterization and function. c10f.b012 application not ready application on device not ready check the specified channel of the device, the devices con- nected to the module, the paramete rs of the specified device as well as the connected sensors and actuators. delay the start after power on or replace the device. see corresponding data sheet. c10f.b013 local bus device power on reset local bus de- vices causes a restart the specified device executed a reset due to a fault or insuffi- cient voltage supply. check the power supply. find the cause by checking th e power supply to the devices and check whether they conform to the nominal value of the permissible ac component. check the power supply unit of the bus coupler for overload (see corresponding data sheet). transmission error check the system and replace devices, if necessary. c109.b022 communication error multiple transmission error bus errors occurred. the system has transmission errors. check the segment, shielding of the bus cables, grounding/ equipotential bonding, connecto rs, communications power (for power drops), fo assembly, as well as the remote bus devices and whether the devices are aligned correctly. c10f.b023 data communication error i/o commu- nication error check the system, shielding of the bus cables, connectors, grounding/equipotentia l bonding, voltage supply of the periph- ery and the voltage supply of the inputs/outputs. replace devices if necessary. c10f.b024 management com- munication error strong inter- ference in local bus communica- tion check the system, shielding of the bus cables, connectors, grounding/equipotentia l bonding, voltage supply of the periph- ery and the voltage supply of the inputs/outputs. replace devices if necessary. configuration errors c10f.b030 configuration error configura- tion errors the configuration is invalid. repl ace device or modify configu- ration.
axl f bk s3 105610_en_02 phoenix contact 15 10.7 diagnose: peripher y and channel error periphery and channel error can only occur once for each i/ o module or channel. in accordance with the sercos specification, errors and messages are mapped in diagnostic idns s-0-0390, s-0- 0095, s-1500.0.32, and s-1500.0.33. the messages are also entered in idns s-0-1303.0.10, s-0- 1303.0.11, and s-0-1303.0.12. you can also read out module-specific diagnostics via idn p-1-0024.x.0. access pdi object 0018 hex (diagstate) with idn p-1- 0024.x.0 via the mapping method. see ?mapping method? section and module-specific data sheet. 10.8 sercos address you can configure the sercos address assignment manually or remotely, see section ?configuration via rotary coding switch?. the sercos address is saved retentively. 10.9 password (idn/s-0-0267) in the default setting some module parameters are write- protected with a password. the default password is pw170875. the following idns are password protected: general errors c10f.b041 hardwar e error hardware fault replace the device. c10f.b042 firmwar e error firmware error replace the device. c10f.b043 local bus is running asynchronously (in relation to the ser- cos bus cycle) local bus is running asynchro- nously (in re- lation to the sercos bus cycle) check the time parameters and adapt them, if necessary. manufacturer-specific errors 400f.0a73 not supported local bus slave at slot: x axioline f module at slot x is not supported; x = slot of the first non-sup- ported mod- ule at least one old, non-supported module is located in the axi- oline f station. replace the module for a module with a current hardware/firm- ware version. sercos diagnostic code (idn s-0- 0390.0.0) [hex] message meaning corrective for an automatic address assignment de- scription, please refer to the documentation of your sercos master. idn description p-0-2000.0.1 update procedure command
axl f bk s3 105610_en_02 phoenix contact 16 11 sercos parameter the following table lists all sercos parameters (s parameters) with important features that ha ve been implemented into the bus coupler. idn name default values unit s-0-0014 interface status - - s-0-0017 idn list of all operation data - - s-0-0021 idn list of invalid operation data for cp2 - - s-0-0022 idn list of invalid operation data for cp3 - - s-0-0025 idn list of all procedure commands - - s-0-0095 diagnostic message - - s-0-0099 reset class 1 diagnostic (process command) - - s-0-0127 cp3 transition check (process command) - - s-0-0128 cp4 transition check (process command) - - s-0-0187 idn list of configurable data as producer - - s-0-0188 idn list of configurable data as consumer - - s-0-0267 password pw170875 - s-0-0279 idn-list of password protected data - - s-0-0390 diagnostic number - - s-0-0420 activate parameterization level procedure command (pl) - - s-0-0422 exit parametrization level procedure command - - s-0-0423 idn-list of invalid data for parametrization level - - s-0-0425 sub-device state machine control - - s-0-1000 scp type & version - 0201 hex , 0202 hex , 0203 hex , 0301 hex , 0302 hex , 0501 hex , 0801 hex , 1801 hex , 0e01 hex , 1601 hex , 1a01 hex , 1901 hex s-0-1002 communication cycle time (t scyc ) - s s-0-1003 allowed mst losses in cp3/cp4 10 - s-0-1005 minimum feedback processing time (t5) 250 000 s s-0-1006 at0 transmission starting time (t1) - s s-0-1007 feedback acquisition capture point (t4) - s s-0-1008 command value valid time (t3) - s s-0-1009 device control (c-dev) offset in mdt - - s-0-1010 length of mdts - - s-0-1011 device status (s-dev) offset in at - - s-0-1012 length of ats - - s-0-1013 svc offset in mdt - - s-0-1014 svc offset in at - - s-0-1015 ring delay - s s-0-1016 slave delay - s s-0-1017 nrt transmission time 650 000 950 000 s s-0-1019 mac address 00.a0.45.xx.xx.xx - s-0-1020 ip address 192.168.0.10 - s-0-1020.0.1 current ip address 192.168.0.10 - s-0-1021 subnet mask 255.255.255.0 - s-0-1021.0.1 current subnet mask 255.255.255.0 - s-0-1022 gateway address 192.168.0.1 - s-0-1022.0.1 current gateway address 192.168.0.1 -
axl f bk s3 105610_en_02 phoenix contact 17 s-0-1023 sync jitter 1000 s s-0-1024 sync delay measuring procedure command (process command) - - s-0-1026 version of communication hardware - - s-0-1027.0.1 requested mtu - - s-0-1027.0.2 effective mtu - - s-0-1028 error counter mst-p/s - - s-0-1031 test pin assignment port 1 and port 2 - - s-0-1035 error counter port1 and port2 - - s-0-1036 inter frame gap - - s-0-1037 slave jitter -- s-0-1040 sercos address 1 - s-0-1041 at command value valid time (t9) - s s-0-1044 device control - - s-0-1045 device status -- s-0-1047 maximum consumer activation time (t11) - s s-0-1048 activate network settings - - s-0-1050.x.1 connection setup - - s-0-1050.x.2 connection number - - s-0-1050.x.3 telegram assignment - - s-0-1050.x.4 max. length of connection - - s-0-1050.x.5 current length of connection - - s-0-1050.x.6 configuration list - - s-0-1050.x.8 connection control - - s-0-1050.x.9 connection state - - s-0-1050.x.10 producer cycle time - s s-0-1050.x.11 allowed data losses - - s-0-1050.x.12 error counter data losses - - s-0-1050.x.13 configuration list for sync - - s-0-1051 image of connection setups - - s-0-1300.0.1 component name sercos bus coupler - s-0-1300.0.2 vendor name phoenix contact - s-0-1300.0.3 vendor code 200 - s-0-1300.0.4 device name axl f bk s3 - s-0-1300.0.5 device id 2701686 - s-0-1300.0.6 connected to subdevice - - s-0-1300.0.7 function revision - - s-0-1300.0.8 hardware revision - - s-0-1300.0.9 software revision - - s-0-1300.0.10 firmware loader revision - - s-0-1300.0.11 order number 2701686 - s-0-1300.0.12 serial number xxxx... - s-0-1300.0.20 operational hours - h s-0-1300.0.134 fibo version info - - s-0-1300.x.1 component name xxxx... - s-0-1300.x.2 vendor name xxxx... - s-0-1300.x.3 vendor code xxx - s-0-1300.x.4 device name xxxx... - s-0-1300.x.5 device id xxxx... - s-0-1300.x.7 function revision - - s-0-1300.x.8 hardware revision - - idn name default values unit
axl f bk s3 105610_en_02 phoenix contact 18 s-0-1300.x.9 software revision - - s-0-1300.x.11 order number xxxx... - s-0-1300.x.12 serial number xxxx... - s-0-1301 list of gdp classes & version 0101 hex - s-0-1302.0.1 fsp type & version 00010001 hex - s-0-1302.0.2 function groups s-0-1500.0.0 - s-0-1302.0.3 application type modular io station - s-0-1303.0.01 diagnosis trace configuration - - s-0-1303.0.02 diagnosis trace control - - s-0-1303.0.03 diagnosis trace state - - s-0-1303.0.10 diagnosis trace buffer no1 - - s-0-1303.0.11 diagnosis trace buffer no2 - - s-0-1303.0.12 diagnosis trace buffer no3 - - s-0-1305.0.1 sercos current time - - s-0-1305.0.2 sercos current fine time - - s-0-1320 list of available energy modes - - s-0-1321.0.6 power consumption - - s-0-1322 procedure command change energy mode - - s-0-1322.0.1 list of supported command types - - s-0-1322.0.2 command type selection for procedure command change energy mode - - s-0-1322.0.3 target energy mode for procedure command change energy mode - - s-0-1323.0.1 current energy mode - - s-0-1500.0.1 io control - - s-0-1500.0.2 io status -- s-0-1500.0.3 list of module type codes - - s-0-1500.0.5 container output data - - s-0-1500.0.9 container input data - - s-0-1500.0.19 parameter channel receive - - s-0-1500.0.20 parameter channel transmit - - s-0-1500.0.23 local bus cycle time - s s-0-1500.0.32 io diagnostic message - - s-0-1500.0.33 current io diagnostic message - - s-0-1500.0.128 local bus error continue mode - - s-0-1501 i/o function group unknown - - s-0-1502 i/o function group digital output - - s-0-1503 i/o function group digital input - - s-0-1504 i/o function group analog output - - s-0-1505 i/o function group analog input - - s-0-1506 i/o function group counter - - s-0-1507 i/o function group complex protocol - - s-0-1508 i/o function group sub bus master - - s-0-1509 i/o function group sub bus slave - - s-0-1512 i/o function group plc module - - s-0-1513 i/o function group motor starter - - s-0-1514 i/o function group pwm (pulse width modulation) - - s-0-1515 i/o function group positioning - - s-0-1516 i/o function group passive - - p-1-x.y.z sercos svc/pdi 1:1 mapping (x ? = ? pdi-index, y ? = ? module slot, z ? = ? subindex) - - p-0-2000.0.1 update command (process command) - - idn name default values unit
axl f bk s3 105610_en_02 phoenix contact 19 s-0-1050.x.1 (connection setup) the following connection types (bit 0 and 1 of idn s-0- 1050.x.1) are supported: ? producer cycle, synchronous operation (clock synchronous, 00 bin ) ? asynchronous operation without watchdog (non-cyclic type ? 2, 10 bin ) s-0-1500.0.128 (local bu s error continue mode) this idn defines the behavior after a bus error. you can find further information on sercos in the um de sercos sys user manual. = 0: the data transfer is on ly started once the error has been removed and the s-0-0099 command has been executed. = 1: the data transfer is started automatically once the error has been removed.
axl f bk s3 105610_en_02 phoenix contact 20 12 access to pdi objects you can access pdi objects from the modules of a station via sercos. you have two options here: 13 mapping method you can use the mapping method for pdi objects with the index 0001 hex ... 1000 hex (1 dec ... 4096 dec ). in the bus coupler, these pdi objects are mapped to the manufacturer-specific parameters p-1-x.y.z. this means that you have read and/or write access to the pdi objects via the manufacturer-specific parameters p-1- x.y.z . 13.1 description of parameter p-1-x.y.z function you can use this parameter to access pdi objects with index 0001 hex ... 1000 hex . attributes after the idn has been sent, th e result is shown in the idn. 13.2 example: read pdi object read the order number of the first module after the bus cou- pler. the parameter to be sent is p-1-0010.1.0. the contents of the object are reported as the result in the idn. - mapping method - simple method - for pdi objects with the index 0001 hex ... 1000 hex - tunnel method - more complex method - for all pdi objects for an overview of the pdi objects of a mod- ule, please refer to the module-specific data sheet. you can find further information on sercos in the um de sercos sys user manual. p-1-x.y.z sercos svc/pdi 1:1 mapping x pdi index (decimal) p-1-0001.y.z ... p-1-4096.y.z y module slot bus coupler: y = 0 1st module after the bus coupler: y = 1 : 63rd module after the bus coupler: y = 63 zsubindex example: p-1-0010.15.0 length maximum number of elements is device-specific current length variable format object-specific function parameter changeability yes executability communication phases cp2, cp3, cp4 x pdi index 000a hex = 0010 dec y module slot; 1st module 1 z pdi subindex 0 byte contents (hex) meaning 0 32 order no. 2688161 136 238 338 431 536 631 7 00 zero-terminated
axl f bk s3 105610_en_02 phoenix contact 21 14 tunnel method 14.1 tunnel method you can use the tunnel method for all pdi objects. you tunnel the pdi object through the function groups of the fsp_i/o, i.e. ? through idns s - 0 - 1501 to s - 0 - 1516. if a module is assigned to se veral function groups, the pdi objects can be read via each assigned function group. 14.2 structure of idn s-0-15xx.y.20 command code parameter count number of following parameters in words reserved (slot) it is not necessary to specify the slot number because it is taken from the idn (y). if yo u enter a value that does not equal 00 hex in byte ? 5, this value is overwritten internally by the slot number specified by y. subslot specify a subslot if you wish to access a submodule (e.g., ? io-link). not used at present (= ? 0). pdi object index see module-specific data sheet. pdi object subindex see module-specific data sheet. see user manual, sercos system manual for i/o devices. amount of data to be written in bytes data to be written s-0-15xx.y.20 parameter channel transmit transferring data to the parameter chan- nel via the service channel. the re- sponse is in s-0-15xx.y.19. s-0-15xx.y.19 parameter channel receive read the response via the service chan- nel after transmitting idn s-0-15xx.y.20. y module slot 1st module after the bus coupler: y = 1 : 63rd module after the bus coupler: y = 63 the parameters are described in the ?sercos system manual for i/o devices? user manual. byte meaning 0 service command code (high byte) 1 service command code (low byte) 2 parameter count (high byte) 3 parameter count (low byte) 4 reserved 5 reserved (slot) 6subslot 7 reserved 8 pdi object index (high byte) 9 pdi object index (low byte) 10 pdi object subindex 11 amount of data to be written in bytes 14 ... xxxx data to be written 0041 hex read pdi object 0042 hex write pdi object for command 0041 hex :00 hex for command 0042 hex : amount of data to be written in bytes for command 0041 hex : not available for command 0042 hex : data to be written
axl f bk s3 105610_en_02 phoenix contact 22 14.3 structure of idn s-0-15xx.y.19 command code parameter count number of following parameters in words ... (copy) copy of request from idn s-0-15xx.y.20 amount of data read in bytes error class, error code read data or additional code should an error occur, the error message details the error class, error code, and addition al code. potential errors are listed in the following table. byte meaning 0 service command code (high byte) 1 service command code (low byte) 2 parameter count (high byte) 3 parameter count (low byte) 4 reserved (copy) 5slot 6subslot (copy) 7 reserved 8 pdi object index (high byte) (copy) 9 pdi object index (low byte) (copy) 10 pdi object subindex (copy) 11 amount of data read in bytes 12 error class 13 error code 14 ... xxxx read data or additional code 8041 hex response to ?read pdi object? 8042 hex response to ?write pdi object? for command 0041 hex : amount of data read in bytes for command 0042 hex :00 hex for an error: 00 hex = 0000 hex : no error; positive response 0000 hex : an error has occurred; negative response positive response for command 0041 hex : read data for command 0042 hex : not available negative response byte 14, 15 additional error code
axl f bk s3 105610_en_02 phoenix contact 23 error messages error class (hex) error code (hex) additional code (hex) meaning 00 00 0000 no error 05 02 0031 permissible length exceeded. object cannot be read completely. 06 02 00a2 hardware fault 03 0000 write and fetch not supported 06 05 0000 inconsistent object attributes 0011 subindex is not supported 0012 code is not a request 0013 a reserved bit has been used 0014 subslot not supported 0015 read/write service type is not supported 0016 index of request fetch service does not equal 0000 hex 0017 length for read or fetch service does not equal zero 0018 length does not correspond to the ob ject length which has been read from the eeprom 0019 read only object cannot be overwritten 07 0000 object does not exist 08 01 0000 error writing the object 00a2 error reading the object 0f 00 0000 error cannot be assigned 04 0000 inconsistent parameters 05 0000 invalid parameters 06 0000 access not supported 11 0000 invalid device 12 0000 timeout 21 0000 invalid slot number 22 0000 slot is not active 23 0000 invalid data length 24 0000 invalid parameter counter
axl f bk s3 105610_en_02 phoenix contact 24 14.4 example: read pdi object read the order number of the first module after the bus cou- pler. read request in this example, the first module is a digital output module. therefore, idn s-0- 1502.1.20 is used. response the result is stored in idn s-0-1502.1.19. - positive response ? negative response byte contents (hex) meaning 000 coderead pdi object 141 2 00 parameter count 4 words follow 304 4 00 reserved ? 500 6 00 subslot no subslot 7 00 reserved ? 8 00 pdi object index 000a: order number 90a 10 00 subindex no subindex 11 00 amount of data to be written in bytes read, therefore = 00 ensure that a write request always contains an even number of bytes. top up with an ad- ditional byte if necessary. if you transmit an uneven number of bytes, you will receive a negative response with a corresponding error message. the response always co ntains an even byte count. a byte with 00 hex is added if necessary in order to top up to an even byte number. byte con- tents (hex) meaning 0 80 code response to ?read pdi object? 141 2 00 parameter count 9 words follow 309 4 00 reserved copy 5 01 slot slot (y from idn) 600 subslot copy 7 00 reserved copy 8 00 pdi object index copy 90a 10 00 pdi object subin- dex copy 11 08 amount of data read in bytes 8 bytes of read data 12 00 result no error 13 00 14 ... 21 32 36 38 38 31 36 31 00 read data order number (8 ? bytes, including zero termination) e.g., 2688161 byte con- tents (hex) meaning 0 80 code response to ?read pdi object? 141 2 00 parameter count 6 ? words follow 306 4 00 reserved copy 5 01 slot slot (y from idn) 600 subslot copy 7 00 reserved copy 8 00 pdi object index copy 90a 10 00 pdi object subin- dex copy 11 00 amount of data read in bytes no data read 12 xx error class error message 13 xx error code 14 xx additional error code 15 xx
axl f bk s3 105610_en_02 phoenix contact 25 15 reset button the reset button is located beneath the top marking label on the bus coupler. figure 6 reset button 1 labeling field 2 reset button the reset button has two functions: ? restarting the bus coupler ? resetting of the default settings 15.1 restarting the bus coupler the bus coupler is restarted when the button is pressed dur- ing operation. the outputs of the station are set to the parameterized sub- stitute values. the process image of the inputs is not re-read. 15.2 restoring the default settings the bus coupler is supplied with the following default set- tings: holding down the button during the initialization phase re- stores the default settings. if you wish to restore the default settings, proceed as fol- lows: ? disconnect the power to the module. ? press and hold the reset button. ? switch on the power. the leds indicate the initialization phase: ? when the rdy led lights up green, release the button. the default settings are restored. 2 1 default values (default settings) s-0-1019 00-a0-45-xx-xx-xx mac address s-0-1020 192.168.0.10 ip address s-0-1021 255.255.255.0 subnet mask s-0-1022 192.168.0.1 gateway address s-0-1040 1 sercos address s-0-0267 pw170875 password s-0-1302.0.3 modular io station application type led state meaning rdy off starting firmware rdy flashing initializing firmware rdy green initialization complete
axl f bk s3 105610_en_02 phoenix contact 26 16 service interface the service interface is loca ted beneath the top marking field on the bus coupler. the service interface is used for later applications. figure 7 service interface 1 labeling field 2 service interface 17 startup 17.1 starting the firmware the firmware is started after you have supplied power to the bus coupler. the bus coupler is ready for operation when the rdy led lights up permanently green. 17.2 basic configuration the bus coupler executes the basic communication after switching on the bus coupler or after resetting with the reset button and the first entry into the cp2 communication phase. these means: ? the corresponding i/o function groups and the struc- ture elements are generated for all devices detected on the local bus. ? channel number and width correspond to the detected data widths of the devices. ? the input/ output process data of all i/o function groups are configured via io_fg. x.2 for mapping in s-0- 1500.0.5 (container output data) or s-0- 1500.0.9 (con- tainer input data). ? the content and lengths of the input/output process data on the local bus are ma pped to sercos according to the sercos profile. ? local bus devices are not parameterized. the devices can be parameterized in cp2 or cp3. by switching over the communication phases to cp3 and subsequently cp4, the sercos master now has the possibil- ity to accept this configuration for realtime operation un- changed or to make changes and to activate them before switching to cp3 via process command s-0-1500.0.12 (re- arrangement of io resource). 17.3 sending bootp requests on startup, the bus coupler sends three bootp requests. if it receives a bootp respon se, the new ip parameters (ip address, subnetwork mask) are saved. if the bus coupler does not receive a response, it starts with the previous configuration. a bootp server must be available to respond to a bootp re- quest. 2 1
axl f bk s3 105610_en_02 phoenix contact 27 17.4 modifying ip parameters the following idns for ip parameters are implemented on the bus coupler: the default settings of the relevant idns are identical. the bus coupler functions with the ip parameters stored in idns s-0-1020.0.1, s-0-102 1.0.1, and s-0-1022.0.1 if you wish to modify one or more ip parameters, proceed as follows: ? adjust the ip parameters in idns s-0-1020, s-0-1021, and s-0-1022. ? execute procedure command s-0-1048 (activate net- work settings). in doing so, at the same time, all modified ip parameters are applied as current ip parameters and the bus coupler now functions with the modified settings. ip parameters current ip parameters default setting s-0-1020 ip address s-0-1020.0.1 cu rrent ip addr ess 192.168.0.10 s-0-1021 subnet mask s-0-1021.0.1 cu rrent subnet mask 255.255.255.0 s-0-1022 gateway address s-0-1022.0.1 current gateway ad dress 192.168.0.1
axl f bk s3 105610_en_02 28 phoenix contact gmbh & co. kg ? 32823 blomberg ? germany phoenixcontact.com 18 firmware update 18.1 firmware update according to sercos specifi- cation the firmware update is carried out in accordance with the procedure described in the se rcos specification. this means that a tftp server is implemented on the bus cou- pler, which can receive files from any tftp client. the file for the update is saved by the bu s coupler in the file system, verified, and, if found to be valid, transferred to the program code area of the memory duri ng the boot phase following a reset (power down). this process can take a few minutes. update requirements ? in the following, the term "pc" will be used as a general term for a pc and notebook, or similar. ? to make sure that no settin gs are lost during updating, take suitable measures to back up the device settings. ? in order to establish a connection to the bus coupler, it may be necessary to deactivate the firewall of your pc. ? current firmware update file is available from the down- load area of the bus coup ler at phoenixcontact.net/ products. transfer file for firmware update to the bus coupler (using windows xp) ? save the current firmware update file to your pc. ? rename the file c2701686.fw. ? connect the bus coupler to the the lan card of your pc via an ethernet cable. ? switch on the power supply to the bus coupler. ? make sure that the ip address of your pc is in the same ip address space as the bus coupler, which you wish to update. ? run the command console of your pc. ? enter the following command line: ? once the firmware file has been successfully trans- ferred, restart the bus coupler by resetting the voltage or execute idn/p-0-2000.0.1. firmware update after the bus coupler restart, the firmware update is per- formed automatically. the firmware update is automatically completed with a bus coupler restart. the status leds signal the curre nt status of the firmware up- date. led states during firmware update note: potential damage to the device if the bus coupler is disconnected from the supply voltage during the firmware update, the bus coupler may be destroyed. ? never disconnect the bus coupler from the supply voltage during the firmware update. if you are using windows ? 7 or windows ? 8: make sure that the ?tftp client? check box is activated in the control panel under ?activate or deactivate windows functions?. ? tftp -i put ? ip address ip address of the bus coupler ? file name name of the update file ? example: tftp -i 192.168.0.2 put c2701686.fw ? the update file is transmitted as quickly as possible to the nrt to cp2 modes. the transmission is complete as soon as the next command line appears in the command console of your pc. rdy led meaning flashing yellow/red incorrect update file downloaded to bus coupler. yellow flashing firmware update is being performed. green on device is ready for operation.

▲Up To Search▲

Price & Availability of 0801831

	To Download 0801831 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .